Using an LDAP Server as Your JNDI Service Provider

You can use an LDAP server as your JNDI service provider for storing connection information for the JDBC Client. This information has been taken from RFC 2713 Schema for Representing Java Objects in an LDAP Directory, which can be found at http://www.faqs.org/rfcs/rfc2713.html.

NOTE: The SequeLink Server for DB2 on z/OS cannot be configured to support SSL. Do not use the encrypted encryption attribute in a DB2 for z/OS configuration.

An example of an LDAP schema definition for JDBC is shown below:

dn: cn=DB2V8 on belg-keidis,ou=JVS,ou=Arne,ou=USERS,o=Development 
cn: DB2V8 on belg-keidis 
objectClass: top 
objectClass: javaContainer 
objectClass: javaObject 
objectClass: javaNamingReference 
javaReferenceAddress: #0#description# 
javaReferenceAddress: #1#portNumber#6007 
javaReferenceAddress: #2#serverName#belg-keidis 
javaReferenceAddress: #3#databaseName#jvs 
javaReferenceAddress: #4#serverDataSource#Default 
javaReferenceAddress: #5#encrypted#1 
javaFactory: com.ddtek.jdbcx.sequeLink.SequeLinkDataSourceFactory 
javaClassName: com.ddtek.jdbcx.sequelink.SequeLinkDataSource